home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Atari Mega Archive 1
/
Atari Mega Archive - Volume 1.iso
/
lists
/
gem
/
l_0799
/
767
< prev
next >
Wrap
Text File
|
1994-08-27
|
3KB
|
102 lines
Subject: Re: Buttons Buttons Buttons
Date: Thu, 14 Jul 1994 13:09:34 +1000
From: Warwick Allison <warwick@cs.uq.oz.au>
Precedence: bulk
Ofir Gal wrote:
>Warwick:
>>This is an incredible waste of a button. It also violates the principle
>>of not requiring the user to hold down multiple buttons to perform an
>>action.
>
>I totally disagree, I wouldn't want Papyrus to work in any other way. It
>doesn't violate anything, this is the way the desktop has behave for the
>last 5 years.
This existed as an undocumented `feature' for a long time. Do people
seriously USE this? How does it correlate to real world semantics?
If an application CAN be clicked on background windows (ie. it does the
correct redraw clipping), then why insist that it be topped? If an
application CANNOT be clicked on background windows, then you don't
need a binding for it.
>>>3. Allow the right button to be used on background windows without topping
>>
>>Totally confusing. All you need to do is allow the user to use the window
>>title, or any unused area of the window to top the window. In an extreme
>>case, also allow a meta key, such as Alt-Ctrl to make the left button top
>>the window.
>
>Why? And what is an 'unused' part of a window?
For example, if there is a dialog in a window, the background of the
dialog (ie. not buttons) is `unused'. The user might also be able to
click on the title bar (thus topping). Only in extreme cases is a
window so obscured that it cannot be topped, and
left-button-tops-window doesn't save all those cases - window totally
obscured. In these extremes, the user can also choose to BOTTOM the
obscuring window. My point is that there are many ways for the user to
top a window, and reserving the left click for this purpose is a waste.
The choices are:
1.
Left click:
IF window on top OR window is toolbox OR right-button-held
THEN click
ELSE top window
Right click:
Ignored. (has to be - otherwise how does the user hold it
down before left-clicking!)
or 2.
Left click:
IF click on something in window
THEN click
ELSE top window
Right click:
Anything else.
IMO, (2) is FAR better than (1).
>>If you use MultiTOS, you'll soon become tired of topping windows if you
>
>I understand what you are saying, but I don't think that poping menus with
>the right button is more useful. Under MTOS you can use WF_BEVENT which
>works well for toolbars, etc.
More useful than doing nothing at all?
>>The sad thing is that many Atari users currently use exactly this.
>>That's why so many programs only run is certain ST resolutions. But
>
>What has mouse button response to do with screen resolutions? All the
>programs I have run happily in 880*656 and still manage to follow this
>standard mouse behaviour.
It's NOT A STANDARD. It is an ACCIDENT that Atari implemented but didn't
document. Try this experiment:
1. Choose a non-Atari user, tell them this feature.
- Measure how loudly they laugh.
2. Choose an Atari user, tell them this feature.
- Measure how suprised they are.
X windows users will laugh the loudest.
On average, Atari users will be suprised.
Hypothesis: The feature is either laughable or unknown.
Two things I would hate to see in a standard.
--
Warwick